-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: fix insecure RUNPATH #3212
Conversation
Closes: https://bugs.gentoo.org/945698 Fixes: df24c1f Upstream-PR: jqlang/jq#3212 Signed-off-by: orbea <[email protected]>
[sam: Add revbump.] Closes: https://bugs.gentoo.org/945698 Fixes: df24c1f Upstream-PR: jqlang/jq#3212 Signed-off-by: orbea <[email protected]> Closes: #39565 Signed-off-by: Sam James <[email protected]>
@orbea Sorry, I'm trying to catch up the issue but I can't understand well. Could you explain the issue and why we have to remove the flag? |
In Gentoo -static-libtool-libs causes a QA Notice. * QA Notice: The following files contain insecure RUNPATHs * Please file a bug about this at https://bugs.gentoo.org/ * with the maintainer of the package. * /var/tmp/portage/app-misc/jq-1.7.1/image/usr/bin/jqn RPATH: /var/tmp/portage/app-misc/jq-1.7.1/work/jq-jq-1.7.1/.libs Gentoo-Issue: https://bugs.gentoo.org/945698 Signed-off-by: orbea <[email protected]>
The |
Was added in 5d9ec83 unclear why. Seem ok to me to remove. I wonder if we should have a CI test that verify that the resulting binary actually is static? inspect the binary or maybe run the binary in a scratch container etc? |
If the intent is that the binary is built entirely statically then I think the correct flag is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for explanation. LGTM!
In Gentoo -static-libtool-libs causes a QA Notice.
Gentoo-Issue: https://bugs.gentoo.org/945698